Alright, I do understand why jsx-a11y/click-events-have-key-events is needed. But why do we need this one? There's no rationale in the commit message.

In our case we sometimes use click events on li, div, ul, etc elements which are not called non-interactive-elements. Since we can't move this events to other elements and we have this eslint rule enabled we will have an error. But with this rule disabled its possible for us to use such events

If I'm not mistaken, cors is default value. I'd suggest to do not mention this, as we don't set it explicitly for other requests we make.

will remove

Can we use quotes here? Just to be consistent with 'Content-Type'.

Our lint will throw an error if I will use quotes here

🤦‍♂️

we can add rule to always use quotes for values if this will help feel better

sure, but not this time.

Geez.. I'm not insist, but using plain if would be more readable (and readability matters!).

onInputChange(e) {
  const { name, value } = e.target;

  if (name === 'tags') {
    value = value.split(',').map(item => item.trim())
  }

  this.setState({ [name]: value })
}

will change, but not exactly like you proposed, since value variable already defined this will occur an error

Why name is wrapped in brackets (i.e. [name])?

I want to reuse this function for a few similar inputs, and I want to set their values in state, so I will have: {tags: some_value} and {title: some_other_value}.
If I will use name without [] it will think that I want this {name: some_value}.
In this case js syntax lets me to use name as different key

Oh, gosh, Jesus.. so basically if you use name without brackets, it will think that name is a name of key?

yeap, exactly

🤦‍♂️ what a silly language

I'd add few lines with explanations why preventDefault() is necessary. If I'm not mistaken it's because we don't want to follow default HTML behavior when form data is submitted to specified URI using POST and multipart/form-data content type.

hm.It seems obvious to me

Why do we need this ignore rule in two places?

because our lint checker creates to error messages for those two lines

I think I have few questions here:

• Why do we need to wrap index in brackets (i.e. [index])? What does it mean? Why just not index?
• Why does activeItem is an object with just one bool which can't be even false? I'd suggest to use the following schema:

  this.setState({ activeIndex: index })

  What do you think?
• It seems like index is not read from state, so why define one?

1. look on one of answers above about these [] brackets;
2. and 3. Take a look on line 39 where I check is newly selected item has appropriate index, in this way I can avoid additional loops that will do nothing more than remove active class from previous item